The following system utilities can only be run from the \\Inetpub\wwwroot\mill\tools directory on the IIS. Once you have located the utility you may double-click the executable to open the utility.
When the Abila Millennium IIS is initialized, the set of standard lookup tables are all loaded into the system cache, to be available for immediate access to users. (This is true for all lookup tables, except the Value-based (super) Lookup Tables, which the software accesses via more specific queries as needed.) The Test Lookup Cache utility examines the set of lookup tables that are currently being held in the cache, and displays a listing of those tables. In addition, a few of the system tables are also held in the cache and included in the listing when the utility is run. This allows you and/or our Customer Support staff to verify that all such tables have been correctly created and cached on your system.
The Test Lookup Cache utility (Milltest.exe) can only be run from the inetpub\wwwroot\mill\tools folder on the IIS. Once you locate the Milltest.exe and double-click and the system will automatically examine the system cache and produce a listing in the display area.
When the utility has completed, at the bottom of the listing, the message, 'Done!' is followed by the processing time, the combined number of rows in all tables, and the number of buffers used in the cache. That statistical information will be specific to your institution. The listing of lookup tables should be standard to any Abila Millennium system, and the utility will be looking for a specific set of tables. If any of the expected tables is not found, an error message will be shown in the listing.
This utility is used to create empty Abila Millennium Database Schema, as well as a tool for Millennium-specific maintenance. This will create database triggers, constraints, and indexes, needed for the Abila Millennium application to function properly with the database.
After initiating this tool, you will need to select the tables in the left frame that need to be maintained. In the right frame, you should select all applicable.
Note: If you choose the ”r;Create Table” option for any of the Events, Profiles, Membership, Custom Lookups, or Lookups tables, the utility will create an EMPTY table, removing all data. Checking the ”r;Create Table” option for any of the System Tables (systemplate, for example) will create tables with the original default entries. Think twice before using this option.
The Destination should default to your site specific database type (SQL or Oracle). It is advised that you NEVER check the ”Apply with NO CHECK” check box, as this could result in data issues that go undetected because no warnings will be issued during the execution of this tool.
Upon successful completion, you will see the notification, 'Create complete.'
This utility will grant all roles in the userlist permissions to the selected table/view.
A role (also called a security role) defines a set of user accounts and groups with the same access to data. Roles are used to implement end user security by controlling access to data on the database server by users connected with client applications.
Upon successful completion of the utility, you will see the message, 'grant permissions complete.'
This utility is used to create empty tables used for the storage of Prototype rows in Abila Millennium.
Once the utility has completed successfully, you will see the message, 'Prototype complete.'
This utility is used to create the Oracle Global Packages used by all Oracle Abila Millennium Triggers.
A Database Package is a method of gathering and storing related procedures, functions, and other package information together as a unit in the database.
Upon completion of the utility, you should see the message, 'Oracle Package Creation complete.'
This utility is used to create the public synonyms needed within Oracle to access the Database Objects including views and reporting tables.
Synonyms are used to provide an alternate name for an object (AKA for an object).
Upon completion of the utility, you should see the message, 'create public synonyms complete.'
This utility is used to reset the next available Primary Key in the Oracle Sequence tables. The Abila Millennium triggers use the sequences to set the primary key on any row insert.
Sequences are database generated numbers. Typically a table using database generated sequences will auto generate a unique id for a field as the default value for that field. This can be particularly useful if multiple applications access the same database. Using a database managed sequence can help to enforce unique id's across applications all adding to the same database.
To reset your sequence value:
Upon completion of the utility, you should see the message, 'create sequence complete.'